Skip to content
{{BRAND}} Contact

Independent information engineer & maker

Available {{AVAILABILITY}}

I build the thing—and the system that runs it.

Software development, residential construction and woodwork, from one person. Useful when a project needs those to line up rather than pass between suppliers.

{{EMAIL}} What I take on
  • Web development
  • Residential construction
  • Technical leadership
  • Craft woodworking

One practice · no handovers

A Three practices

Three ways the disciplines combine.

Each one pairs two trades. The key on every card names the pair.

A tablet, technical drawings, dividers and callipers on a desk

Software × Team

Tech lead who writes code

Tech Lead and development consultant for governments and businesses, on short fixes and longer programmes. I set the architecture, review the work, and stay close to the code.

  • Technical leadership and architecture
  • Code review and team standards
  • CI/CD, hosting and delivery
  • Tender and vendor support

Example Development lead on public-sector and commercial programmes.

A timber-clad tiny home with a sedum green roof and roof-mounted solar panels, its sliding glass door opening onto a deck

Software × Building

Connected buildings

Tiny homes and residential work with the smart layer designed in rather than added later. Sensors, controls and remote management get specified alongside the framing.

  • Design and build
  • Device, power and network layout
  • Remote monitoring and updates
  • Handover the owner can actually use

Example A tiny home where heating, power and access are managed from one dashboard.

Laser-cut plywood parts laid out flat, still in their cut sheet

Wood × Machine

Products that ship flat

Wooden furniture sets and cut goods, drawn for the machine and the buyer at once. The design doubles as the production file, and the instructions are written for a kitchen table.

  • Design for manufacture
  • Cut files, nested and ready to run
  • Flat-pack assembly instructions
  • Webshop and fulfilment set up

Example DIY furniture kits sold through webshops, from sketch to production run.

Fig. 1 — Workshop

B Why combine them

Projects tend to lose time in the gaps between trades.

Not in the work, in the seams: a spec that reaches site half understood, a drawing redrawn for the machine, an estimate from someone who has not held the tool. Combining the trades removes some of them.

Spec → Site

Fewer handovers
The person writing the specification is often the person on site, so less is lost between the two.

Code → Ship

The code is the specification
Working software communicates better than any document. A prototype in production beats a proposal on paper.

Tool → Estimate

Grounded estimates
Budgets and timelines from someone who has done the physical work, not only specified it.
C How a job runs

Same four steps, whether it is a kit or a programme.

  1. Step 1

    Scope

    A visit or a call, then a written scope with a price and the known risks.

  2. Step 2

    Prototype

    One small real thing first — a working screen, a deployed endpoint, or a test piece.

  3. Step 3

    Build

    Fixed scope, and a short weekly note on what moved and anything that changed the estimate.

  4. Step 4

    Hand over

    Source files, tests and documentation are yours. Support and maintenance if you want it.

Fig. 2 — Build site

D Selected work

Some of what has been built.

Software shipped for governments and businesses, and a deck with the lighting built into it. Photo plates open to the full photograph.

Fig. 3 · Software

Citizen-facing web portal

A self-service portal for a local authority, replacing a paper form process. Twelve thousand submissions in the first year.

Fig. 4 · Software

System integration API

REST and webhook endpoints connecting four legacy systems to a modern front end. Zero-downtime migration from the old integration.

Fig. 5 · Software

Technical architecture review

An architecture report and delivery roadmap for a government programme preparing to scale from pilot to national rollout.

Fig. 6 · Software

CI/CD and hosting setup

Build pipelines, container hosting and monitoring for three production services. From a manual deploy process to a fully automated pipeline.

A large two-level timber deck against a black-clad house, with small lights set into the edge of the step and along the perimeter Full frame

Fig. 7 · Build

Deck with smart lighting

Fittings let into the step edge and the perimeter, so the lighting is part of the structure rather than sitting on it.

A newly built barn clad in black timber on a brick plinth, with a white bargeboard gable, a dormer window, exposed rafter tails on timber corbels and two pairs of white glazed double doors Full frame

Fig. 8 · Build

Barn build

Black timber cladding on a brick plinth, exposed rafter tails, glazed double doors: an outbuilding detailed like a house.

E Capability

Two benches, one person.

Desk

  • Web applications and APIs
  • System architecture and technical review
  • Integrations between systems
  • CI/CD, hosting and monitoring
  • Data modelling and backend services
  • Connected devices and remote management
  • Tech lead and delivery management

Shop

  • Cabinetmaking, joinery and finishing
  • Residential construction and fit-out
  • Prototyping and small production runs
  • Laser cutting and CNC routing
F Contact

Send a drawing, a brief, or a half-formed idea.

No contact form. Mail or call and you reach me directly.

{{EMAIL}}
Title block Sheet 1 of 1
Engineer
{{NAME}}
Practice
{{BRAND}}
Email
{{EMAIL}}
Phone
{{PHONE}}
Based
{{LOCATION}}
Available
{{AVAILABILITY}}